Event planning in a content sharing platform

ABSTRACT

Systems and methods are provided for receiving a selection to add an event invite media overlay to a media content item, receiving content to be added to the event invite media overlay, the content corresponding to an event, and adding to the event invite media overlay, the content corresponding to the event to generate a custom event invite media overlay. The systems and methods further comprise causing display of the custom event invite media overlay on the media content item, receiving at least one user to which to send an invite to the event, and sending, to a second computing device associated with the at least one user, an invite to the event, the invite comprising the custom event invite media overlay and the media content item.

CLAIM OF PRIORITY

This application is a continuation of U.S. application Ser. No.17/222,247, filed Apr. 5, 2021, which is a continuation of U.S.application Ser. No. 16/503,783, filed Jul. 5, 2019, which applicationsare hereby incorporated by reference in their entirety.

BACKGROUND

A content sharing platform may receive millions of messages from usersdesiring to share media content such as audio, images, and video betweenuser devices (e.g., mobile devices, personal computers). A contentsharing platform may further allow users to “chat” with other users byexchanging text messages.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present disclosure and should not be considered aslimiting its scope.

FIG. 1 is a block diagram showing an example networked system forexchanging data (e.g., messages and associated content) over a network,according to some example embodiments.

FIG. 2 is a block diagram illustrating further details regarding themessaging system, according to some example embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored in adatabase of a messaging server system, according to some exampleembodiments.

FIG. 4 is a schematic diagram illustrating a structure of a message,according to some embodiments, generated by a messaging clientapplication for communication.

FIG. 5 is a flow chart illustrating aspects of a method, according tosome example embodiments.

FIGS. 6-21 illustrate example graphical user interfaces (GUIs),according to some example embodiments.

FIG. 22 is a block diagram illustrating an example of a softwarearchitecture that may be installed on a machine, according to someexample embodiments.

FIG. 23 illustrates a diagrammatic representation of a machine, in theform of a computer system, within which a set of instructions may beexecuted for causing the machine to perform any one or more of themethodologies discussed herein, according to an example embodiment.

DETAILED DESCRIPTION

Systems and methods described herein relate to event planningfunctionality in a content sharing platform (e.g., a social mediaplatform). As explained above, a content sharing platform may receivemillions of messages from users desiring to share media content such asaudio, images, and video between user devices (e.g., mobile devices,personal computers, etc.). For example, a user can capture mediacontent, such as an image or video, augment the image or video (e.g.,with text, audio, media overlay or other creative tools) and then send amessage comprising the augmented image or video to one or more otherusers. The user can view messages comprising media content from otherusers and also discover and view media content (e.g., messages and mediacollections) generated by other users or entities related to aparticular interest or topic (e.g., sports, celebrities, food, events).A content sharing platform may further allow users to “chat” with otherusers by exchanging text messages.

Event planning in such a content sharing platform, however, is difficultto do. For example, a user can send a message to one or more usersinviting them to a holiday barbeque or surprise party for a friend, butthere is no easy way to surface important details about the event (e.g.,date, time, location), notify users about updates to the event, showevents on a map, or otherwise provide an easy way to plan and organizean event.

Example embodiments provide functionality in a content sharing platformfor event planning. For example, a user can create a custom event invitemedia overlay that includes content for an event. The custom eventinvite media overlay can be displayed on a media content item (e.g., animage or video) and sent as an invite to one or more other users. A userreceiving the invite can join the event, chat with others that havejoined the event, receive notifications about the event (e.g., updatesto the event, new users joining the event), forward the invite to otherusers, and so forth. Events (e.g., actions) corresponding to the eventcan be logged by a server system (e.g., when a user joins the event,when a user invites another user to the event, when details of the eventchange). Visual indicators of users attending the event can be displayedon a map on the event location. Moreover, users attending the event cancapture media content items that can be automatically added to a mediacollection for the event group. Accordingly, example embodiments includean infrastructure to allow impromptu hangouts with small groups offriends in an informal fashion (e.g., to grab lunch that day, to go tothe movies after work, to grab drinks after work) to more formalinvites, such as for birthday parties or other events.

FIG. 1 is a block diagram illustrating a networked system 100 (e.g., acontent sharing platform or messaging system) for exchanging data (e.g.,messages and associated content) over a network. The networked system100 includes multiple client devices 110, each of which hosts a numberof client applications 114. Each client application 114 iscommunicatively coupled to other instances of the client application 114and a server system 108 via a network 104.

The client device 110 may comprise, but is not limited to, a mobilephone, desktop computer, laptop, portable digital assistant (PDA), smartphone, tablet, ultrabook, netbook, laptop, multi-processor system,microprocessor-based or programmable consumer electronic system, gameconsole, set-top box, computer in a vehicle, wearable device, or anyother communication device that a user may utilize to access thenetworked system 100. In some embodiments, the client device 110 maycomprise a display module (not shown) to display information (e.g., inthe form of user interfaces). In further embodiments, the client device110 may comprise one or more of touch screens, accelerometers,gyroscopes, cameras, microphones, Global Positioning System (GPS)devices, and so forth.

The client device 110 may be a device of a user that is used to createmedia content items such as video, images (e.g., photographs), audio,and media overlays and to send and receive messages containing suchmedia content items, text, media overlays, and so forth, to and fromother users. The client device 110 may be a device of a user that isused to create and edit messages comprising media content, includingvideo, one or more images (e.g., photographs), media overlays or othercreative tools, text, and so forth. The client device 110 may further bea device of a user that is used to view and generate interactivemessages, view other users on a map, chat (e.g., exchange text messages)with other users of the system, generate and view event invites, join anevent, receive notifications related to an event, and so forth.

One or more users may be a person, a machine, or other means ofinteracting with the client device 110. In example embodiments, the usermay not be part of the system 100 but may interact with the system 100via the client device 110 or other means. For instance, the user mayprovide input (e.g., touch screen input or alphanumeric input) to theclient device 110, and the input may be communicated to other entitiesin the system 100 (e.g., third-party servers, the server system 108,etc.) via the network 104. In this instance, the other entities in thesystem 100, in response to receiving the input from the user, maycommunicate information to the client device 110 via the network 104 tobe presented to the user. In this way, the user may interact with thevarious entities in the system 100 using the client device 110.

The system 100 may further include the network 104. One or more portionsof the network 104 may be an ad hoc network, an intranet, an extranet, avirtual private network (VPN), a local area network (LAN), a wirelessLAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), ametropolitan area network (MAN), a portion of the Internet, a portion ofthe public switched telephone network (PSTN), a cellular telephonenetwork, a wireless network, a WI-FI network, a WiMax network, anothertype of network, or a combination of two or more such networks.

The client device 110 may access the various data and applicationsprovided by other entities in the system 100 via a web client (e.g., abrowser, such as the Internet Explorer® browser developed by Microsoft®Corporation of Redmond, Wash. State) or one or more client applications114. The client device 110 may include one or more client applications114 (also referred to as “apps”) such as, but not limited to, a webbrowser, a messaging application, an electronic mail (email)application, an e-commerce site application, a mapping or locationapplication, a media overlay application, an interactive messagingapplication, an image or video capture application, an event planningapplication, and the like.

In some embodiments, one or more client applications 114 may be includedin a given one of the client devices 110, and configured to locallyprovide a user interface and at least some of the functionalities of theapplication, with the client application 114 configured to communicatewith other entities in the system 100 (e.g., third-party servers, theserver system 108, etc.), on an as-needed basis, for data and/orprocessing capabilities not locally available (e.g., to process userqueries, to authenticate a user, to verify a method of payment, etc.).Conversely, one or more client applications 114 may not be included inthe client device 110, and then the client device 110 may use its webbrowser to access the one or more applications hosted on other entitiesin the system 100 (e.g., third-party servers, the server system 108,etc.).

In one example, a client application 114 may be a messaging applicationthat allows a user to take a photograph or video, add a caption orotherwise edit the photograph or video, and then send the photograph orvideo to another user. In one example, the message may be ephemeral andbe removed from a receiving user device after viewing or after apredetermined amount of time (e.g., 10 seconds, 24 hours). An ephemeralmessage refers to a message that is accessible for a time-limitedduration. An ephemeral message may be a text, an image, a video, andother such content that may be stitched or joined together in accordancewith embodiments described herein. The access time for the ephemeralmessage may be set by the message sender. Alternatively, the access timemay be a default setting or a setting specified by the recipient.Regardless of the setting technique, the message is transitory.

The messaging application may further allow a user to create a galleryor message collection. A gallery may be a collection of photos andvideos which may be viewed by other users “following” the user's gallery(e.g., subscribed to view and receive updates in the user's gallery). Inone example, the gallery may also be ephemeral (e.g., lasting 24 hours,lasting for a duration of an event (e.g., during a music concert,sporting event), or lasting another predetermined time).

An ephemeral message may be associated with a message durationparameter, the value of which determines an amount of time that theephemeral message will be displayed to a receiving user of the ephemeralmessage by the client application 114. The ephemeral message may befurther associated with a message receiver identifier and a messagetimer. The message timer may be responsible for determining the amountof time the ephemeral message is shown to a particular receiving useridentified by the message receiver identifier. For example, theephemeral message may only be shown to the relevant receiving user for atime period determined by the value of the message duration parameter.

In another example, the messaging application may allow a user to storephotographs and videos and create a gallery that is not ephemeral andthat can be sent to other users. For example, a user may assemblephotographs and videos from a recent vacation to share with friends andfamily.

The server system 108 may provide server-side functionality via thenetwork 104 (e.g., the Internet or a wide area network (WAN)) to one ormore client devices 110 and/or one or more third-party servers (notshown). The server system 108 may include an application programminginterface (API) server 102, an application server 112, a messagingapplication server 116, a media content processing system 118, and asocial network system 122, which may be communicatively coupled witheach other and with one or more data storages, such as one or moredatabases 120.

The server system 108 may be a cloud computing environment, according tosome example embodiments. The server system 108, and any serversassociated with the server system 108, may be associated with acloud-based application, in one example embodiment.

The one or more databases 120 may be storage devices that storeinformation such as untreated media content, original media content fromusers (e.g., high-quality media content), processed media content (e.g.,media content that is formatted for sharing with client devices 110 andviewing on client devices 110), context data related to a media contentitem, context data related to a user device (e.g., a computing or clientdevice 110), media overlays, media overlay smart widgets or smartelements, user data, user device information, media content (e.g., videoand images), media content data (e.g., data associated with video andimages), computing device context data, serialized data, session dataitems, user device location data, mapping information, interactivemessage usage data, interactive message metrics data, event details andtokens, and so forth. The one or more databases 120 may further storeinformation related to third-party servers, third-party applications,client devices 110, client applications 114, users, and so forth.

The one or more databases 120 may include cloud-based storage externalto the server system 108 (e.g., hosted by one or more third-partyentities external to the server system 108). While the storage devicesare shown as database(s) 120, it is to be understood that the system 100may access and store data in storage devices such as databases 120, blobstorages, and other types of storage methods.

The system 100 may further include one or more third-party servers (notshown). The one or more third-party servers may include one or morethird-party applications. The one or more third-party applications,executing on the third-party server(s), may interact with the serversystem 108 via the API server 102 via a programmatic interface providedby the API server 102. For example, one or more of the third-partyapplications may request and utilize information from the server system108 via the API server 102 to support one or more features or functionson a website hosted by a third party or an application hosted by thethird party. The third-party website or application, for example, mayprovide functionality that is supported by relevant functionality anddata in the server system 108.

Accordingly, each client application 114 is able to communicate andexchange data with other client applications 114 and with the serversystem 108 via the network 104. The data exchanged between clientapplications 114, and between a client application 114 and the serversystem 108, includes functions (e.g., commands to invoke functions) aswell as payload data (e.g., text, audio, video, or other multimediadata).

The server system 108 provides server-side functionality via the network104 to a particular client application 114. While certain functions ofthe system 100 are described herein as being performed either by aclient application 114 or by the server system 108, it will beappreciated that the location of certain functionality either within theclient application 114 or within the server system 108 is a designchoice. For example, it may be technically preferable to initiallydeploy certain technology and functionality within the server system108, but to later migrate this technology and functionality to theclient application 114 where a client device 110 has a sufficientprocessing capacity.

The server system 108 supports various services and operations that areprovided to the client application 114. Such operations includetransmitting data to, receiving data from, and processing data generatedby the client application 114. This data may include message content,client device information, geolocation information, media annotation andoverlays, message content persistence conditions, social networkinformation, live event information, date and time stamps, media content(e.g., video and images), media content data (e.g., data associated withvideo and images), and interactive message usage data, event planningdata, as examples. Data exchanges within the networked system 100 areinvoked and controlled through functions available via user interfaces(UIs) of the client application 114.

In the server system 108, the API server 102 is coupled to, and providesa programmatic interface to, the application server 112. The applicationserver 112 is communicatively coupled to a database server 124, whichfacilitates access to the one or more databases 120 in which is storeddata associated with messages processed by the application server 112.

The API server 102 receives and transmits message data (e.g., commandsand message payloads) between the client device 110 and the applicationserver 112. Specifically, the API server 102 provides a set ofinterfaces (e.g., routines and protocols) that can be called or queriedby the client application 114 in order to invoke functionality of theapplication server 112. The API server 102 exposes various functionssupported by the application server 112, including account registration;login functionality; the sending of messages, via the application server112, from a particular client application 114 to another clientapplication 114; the sending of media files (e.g., images or video) froma client application 114 to the messaging application server 116, forpossible access by another client application 114; the setting of acollection of media data (e.g., a gallery, story, message collection, ormedia collection); the retrieval of such collections; the retrieval of alist of friends of a user of a client device 110; the retrieval ofmessages and content; the adding of friends to and deletion of friendsfrom a social graph; the location of friends within a social graph;opening an application event (e.g., relating to the client application114); mapping data; the creation and generation of a media overlay, andso forth.

The application server 112 hosts a number of applications andsubsystems, including the messaging application server 116, the mediacontent processing system 118, and the social network system 122. Themessaging application server 116 implements a number of messageprocessing technologies and functions, particularly related to theaggregation and other processing of content (e.g., textual andmultimedia content) included in messages received from multipleinstances of the client application 114. The text and media content frommultiple sources may be aggregated into collections of content (e.g.,called stories, galleries, or media collections). These collections arethen made available, by the messaging application server 116, to theclient application 114. Other processor- and memory-intensive processingof data may also be performed server-side by the messaging applicationserver 116, in view of the hardware requirements for such processing.

The application server 112 also includes the media content processingsystem 118, which is dedicated to performing various media contentprocessing operations, typically with respect to images or videoreceived within the payload of a message at the messaging applicationserver 116. The media content processing system 118 may access one ormore data storages (e.g., the database(s) 120) to retrieve stored datato use in processing media content and to store results of processedmedia content.

The social network system 122 supports various social networkingfunctions and services, and makes these functions and services availableto the messaging application server 116. To this end, the social networksystem 122 maintains and accesses an entity graph 304 (depicted in FIG.3) within the database(s) 120. Examples of functions and servicessupported by the social network system 122 include the identification ofother users of the networked system 100 with whom a particular user hasrelationships or whom the particular user is “following,” and also theidentification of other entities and interests of a particular user.

The messaging application server 116 may be responsible for generationand delivery of messages between users of client devices 110. Themessaging application server 116 may utilize any one of a number ofmessage delivery networks and platforms to deliver messages to users.For example, the messaging application server 116 may deliver messagesusing electronic mail (email), instant messaging (IM), Short MessageService (SMS), text, facsimile, or voice (e.g., Voice over IP (VoIP))messages via wired networks (e.g., the Internet), plain old telephoneservice (POTS), or wireless networks (e.g., mobile, cellular, WIFI, LongTerm Evolution (LTE), or Bluetooth).

FIG. 2 is a block diagram 200 illustrating further details regarding thesystem 100, according to example embodiments. Specifically, the system100 is shown to comprise the messaging client application 114 and theapplication server 112, which in turn embody a number of subsystems,namely an ephemeral timer system 202, a collection management system204, and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 114 and the messaging application server 116. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message, or acollection of messages (e.g., otherwise referred to herein as “mediacollections,” “galleries,” “message collections,” “stories,” and thelike), selectively display and enable access to messages and associatedcontent via the messaging client application 114.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image, video, and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text, and audio) may be organized into an“event gallery” or an “event story.” Such a collection may be madeavailable for a specified time period, such as the duration of an eventto which the content relates. For example, content relating to a musicconcert may be made available as a “story” for the duration of thatmusic concert. The collection management system 204 may also beresponsible for publishing an icon that provides notification of theexistence of a particular collection to the user interface of themessaging client application 114.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation (e.g., money, non-money credits or pointsassociated with the messaging system or a third-party reward system,travel miles, access to artwork or specialized lenses, etc.) may be paidto a user for inclusion of user-generated content into a collection. Insuch cases, the curation interface 208 operates to automatically makepayments to such users for the use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the networked system 100. In one example, the annotationsystem 206 operatively supplies a media overlay (e.g., a filter or mediaaugmentation) to the messaging client application 114 based on ageolocation of the client device 110. In another example, the annotationsystem 206 operatively supplies a media overlay to the messaging clientapplication 114 based on other information, such as social networkinformation of the user of the client device 110. A media overlay mayinclude audio and visual content and visual effects. Examples of audioand visual content include pictures, texts, logos, animations, and soundeffects. An example of a visual effect includes color overlaying. Theaudio and visual content or the visual effects can be applied to a mediacontent item (e.g., a photo) at the client device 110. For example, themedia overlay includes text that can be overlaid on top of a photographtaken by the client device 110. In another example, the media overlayincludes an identification of a location overlay (e.g., Venice Beach), aname of a live event, a name of a merchant overlay (e.g., Beach CoffeeHouse), or of a home of a user. In another example, the annotationsystem 206 uses the geolocation of the client device 110 to identify amedia overlay that includes the name of a merchant at the geolocation ofthe client device 110. The media overlay may include other indiciaassociated with the merchant. The media overlays may be stored in thedatabase(s) 120 and accessed through the database server 124.

The annotation system 206 may further enable a user to interact with aninteractive message, such as by adding one or more media content itemsto the interactive message, as described in further detail below. In oneexample embodiment, the annotation system 206 provides a publicationplatform that allows a user or merchant to create an interactive messagewith a plurality of objects associated with the interactive message forwhich users may add personal content. For example, a designer may createa video of a rock band with various interactive objects for differentmembers of the band (a drummer, a keyboard player, a guitarist, etc.).The video of the rock band may be made available to users as aninteractive message.

In one example embodiment, the annotation system 206 provides auser-based publication platform that enables users to select ageolocation on a map and upload content associated with the selectedgeolocation. The user may also specify circumstances under which aparticular media overlay is to be offered to other users. The annotationsystem 206 generates a media overlay that includes the uploaded contentand associates the uploaded content with the selected geolocation.

In another example embodiment, the annotation system 206 provides amerchant-based publication platform that enables merchants to select aparticular media overlay associated with a geolocation via a biddingprocess. For example, the annotation system 206 associates the mediaoverlay of a highest-bidding merchant with a corresponding geolocationfor a predefined amount of time.

FIG. 3 is a schematic diagram 300 illustrating data which may be storedin the database(s) 120 of the server system 108, according to certainexample embodiments. While the content of the database(s) 120 is shownto comprise a number of tables, it will be appreciated that the datacould be stored in other types of data structures (e.g., as anobject-oriented database).

The database 120 includes message data stored within a message table314. An entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events, and so forth. Regardless of type, any entity regardingwhich the server system 108 stores data may be a recognized entity. Eachentity is provided with a unique identifier, as well as an entity typeidentifier (not shown).

The entity graph 304 furthermore stores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization), interested-based, or activity-based, merely for example.

The database 120 also stores annotation data, in the example form ofmedia overlays or filters, in an annotation table 312. Annotation datamay also be referred to herein as “creative tools” or “interactivefeatures.” Annotation data may comprise predefined interactive messagesto be provided to users.

Media overlays or filters, for which data is stored within theannotation table 312, are associated with and applied to videos (forwhich data is stored in a video table 310) and/or images (for which datais stored in an image table 308). Filters, in one example, are overlaysthat are displayed as overlaid on an image or video during presentationto a recipient user. Filters may be of various types, includinguser-selected filters from a gallery of filters presented to a sendinguser by the messaging client application 114 when the sending user iscomposing a message. Other types of filters include geolocation filters(also known as “geo-filters”), which may be presented to a sending userbased on geographic location. For example, geolocation filters specificto a neighborhood or special location may be presented within a userinterface by the messaging client application 114, based on geolocationinformation determined by a GPS unit of the client device 110. Anothertype of filter is a data filter, which may be selectively presented to asending user by the messaging client application 114, based on otherinputs or information gathered by the client device 110 during themessage creation process. Examples of data filters include a currenttemperature at a specific location, a current speed at which a sendinguser is traveling, a battery life for a client device 110, or thecurrent time.

Other annotation data that may be stored within the annotation table 312is so-called “lens” data. A “lens” may be a real-time special effect andsound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe message table 314. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story, gallery, or media collection). The creationof a particular collection may be initiated by a particular user (e.g.,any user for whom a record is maintained in the entity table 302). Auser may create a “personal story” in the form of a collection ofcontent that has been created and sent/broadcast by that user. To thisend, the user interface of the messaging client application 114 mayinclude an icon that is user-selectable to enable a sending user to addspecific content to his or her personal story.

A media or message collection may also constitute a “live story,” whichis a collection of content from multiple users that is created manually,automatically, or using a combination of manual and automatictechniques. For example, a “live story” may constitute a curated streamof user-submitted content from various locations and events. Users whoseclient devices 110 have location services enabled and are at a commonevent location at a particular time may, for example, be presented withan option, via a user interface of the messaging client application 114,to contribute content to a particular live story. The live story may beidentified to the user by the messaging client application 114, based onhis or her location. The end result is a “live story” told from acommunity perspective.

A further type of content collection is known as a “location story,”which enables a user whose client device 110 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

A chat history table 316 stores data related to text messages exchangedbetween users in a “chat” session via the messaging application. Forexample, the chat history table 316 stores all the messages exchangedbetween users, or all messages for a predefined time period (e.g., lasthour, day, week, month, year), so that a user may view a history of textmessages the user exchanged between one or more other users.

An event planning table 318 stores data related to an event. Forexample, the event planning table 318 stores details of an event, loggedevents (e.g., actions) corresponding to the event (e.g., when a userjoins the event, when a user invites another users, when details of theevent change), links to chat sessions for the event (e.g., a link tochat sessions in the chat history table 316), tokens for the event, andso forth.

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some embodiments, generated by a client application 114 forcommunication to a further client application 114 or the messagingapplication server 116. The content of a particular message 400 is usedto populate the message table 314 stored within the database(s) 120,accessible by the messaging application server 116. Similarly, thecontent of a message 400 is stored in memory as “in-transit” or“in-flight” data of the client device 110 or the application server 112.The message 400 is shown to include the following components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text, to be generated by a user via        a user interface of the client device 110 and that is included        in the message 400.    -   A message image payload 406: image data, captured by a camera        component of a client device 110 or retrieved from memory of a        client device 110, and that is included in the message 400.    -   A message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 110 and that is included in the message 400.    -   A message audio payload 410: audio data, captured by a        microphone or retrieved from the memory component of the client        device 110, and that is included in the message 400.    -   Message annotations 412: annotation data (e.g., media overlays        such as filters, stickers, or other enhancements) that        represents annotations to be applied to the message image        payload 406, message video payload 408, or message audio payload        410 of the message 400.    -   A message duration parameter 414: a parameter value indicating,        in seconds, the amount of time for which content of the message        400 (e.g., the message image payload 406, message video payload        408, and message audio payload 410) is to be presented or made        accessible to a user via the messaging client application 114.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message 400. Multiple message geolocation        parameter 416 values may be included in the payload, each of        these parameter values being associated with respective content        items included in the content (e.g., a specific image within the        message image payload 406, or a specific video in the message        video payload 408).    -   A message story identifier 418: identifier values identifying        one or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 406 of the        message 400 is associated. For example, multiple images within        the message image payload 406 may each be associated with        multiple content collections using identifier values.    -   A message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 110 on        which the message 400 was generated and from which the message        400 was sent.    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 110 to        which the message 400 is addressed.    -   An event token (not shown): an identifier (e.g., randomly        generated number) indicative of the event.

The contents (e.g., values) of the various components of the message 400may be pointers to locations in tables within which content data valuesare stored. For example, an image value in the message image payload 406may be a pointer to (or address of) a location within an image table308. Similarly, values within the message video payload 408 may point todata stored within a video table 310, values stored within the messageannotations 412 may point to data stored in an annotation table 312,values stored within the message story identifier 418 may point to datastored in a story table 306, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 302.

FIG. 5 is a flow chart illustrating aspects of a method 500, accordingto some example embodiments. For illustrative purposes, the method 500is described with respect to the networked system 100 of FIG. 1. It isto be understood that the method 500 may be practiced with other systemconfigurations in other embodiments.

In operation 502, a computing device (e.g., client device 110) receivesa selection (e.g., a selection of an option or interface element) to addan event invite media overlay to a media content item. In one exampleembodiment, a user captures a media content item via a camera device ofthe computing device. For example, the user captures an image (e.g.,photograph) or video. The computing device can display the capturedimage or video on a display area of the computing device and provide anoption (e.g., an interface element) to add a media overlay to thecaptured media content item. FIG. 6 illustrates an example display 600on the computing device (e.g., via a graphical user interface (GUI))showing a media content item 602 captured by a camera device of thecomputing device and a menu 604 with options to choose a media overlay(e.g., in the form of a sticker). One of the options in the menu 604 isan option for an event invite media overlay 606. The user can choose oneor more media overlays from the menu 604 to be added to the mediacontent item 602 (e.g., to augment the media content item by overlayingthe media overlay on top of the media content item).

In one example, the user selects the event invite media overlay 606. Thecomputing device receives the selection to add the event invite mediaoverlay to the media content item in operation 502. The computing devicecauses display of a GUI to enter content (e.g., details) for an eventcorresponding to the event invite media overlay. FIG. 7 illustrates anexample GUI 700 for entering content for an event corresponding to anevent invite media overlay 702. For example, a user can enter a title704 for the event, a location 706 (e.g., address) for the event, a time708 for the event, and a description 710 for the event. It is noted thateverything besides the title are optional, and thus, a user can quicklygenerate an event with very little information. In one example, theevent title can even be optional and the computing device can generate adefault tile (e.g., the user's name plus event (e.g., “Nate's Event” or“Sally's Event)) to make it even easier for the user.

In one example, the GUI 700 provides a mechanism to view other eventinvite media overlays that the user created previously. For example, theuser can swipe to the right on the next event invite media overlay 716to view and edit the event invite media overlay 716.

The user can enter any content for the event invite media overlay 702via a keyboard 718 or other means. Once the user has completed enteringany content in the event invite media overlay 702, the user can add itto the media content item (e.g., via a selection option 712). In oneexample, instead of adding the event invite media overlay 702 to themedia content item, the user can send it directly to one or more users(e.g., via a selection option 714).

Once the user selects to add the event invite media overlay to the mediacontent item, the computing device receives the content to be added tothe event invite media overlay, in operation 504, and generates a customevent invite media overlay using the content corresponding to the eventin operation 506. For example, the computing device adds the contentcorresponding to the event (e.g., title, location, date and time) to theevent invite media overlay to create a custom event invite mediaoverlay.

In operation 508, the computing device causes display of the customevent invite media overlay on the media content item. FIG. 8 illustratesan example GUI 800 displaying a custom event invite media overly 802that is displayed on (e.g., overlaid on) a media content item 804. Inthis example, the custom event invite media overlay 802 shows an eventtitle 806, an event location 808, an event date and time 810, an option812 to view details of the event, and an option 814 to join the event.The GUI 800 further includes an option 816 to send the invite to adestination, such as one or more other users.

In one example embodiment, the user can move the event invite mediaoverlay around to different locations on the media content item, rotatethe event invite media overlay (e.g., so that it is at a differentangle), reshape the event invite media overlay to make it smaller orlarger, change the color of the event invite media overlay, change thefont, and so forth. In some example embodiments, the event invite mediaoverlay is automatically resized based on the content provided for theevent. For example, if only a title is provided (or auto-generated), theevent invite media overlay is resized to only show the title. Likewise,if only a title and location are provided, the event invited mediaoverlay is resized to only show the title and location, and so forth,dependent upon the content provided.

Once the user selects to send the invite to a destination (e.g., viaoption 816), the computing device can cause a display of a destinationlist from which the user can select one or more users to which to sendthe invite. FIG. 9 illustrates an example GUI 900 displaying adestination list 902 comprising groups 904 (e.g., predefined groups ofusers), best friends 906 (e.g., user-designated close friends), andcontacts listed in alphabetical order 908. The user can select one ormore groups and/or users to which to send the invite. The GUI 900 alsoprovides an option 910 that the user can select to send the invite oncethe user has selected one or more groups and/or users to which to sendthe invite.

In operation 510, the computing device receives at least one destination(e.g., user or group of users) to which to send the invite to the event.In operation 512, the computing device then sends the invite to a secondcomputing device associated with the at least one destination (e.g., asecond user). The invite comprises the custom event invite media overlayand the media content item.

In one example, the computing device sends the invite via a computingsystem (e.g., server system 108) to the second computing device. In oneexample, the computing device also generates a secure token (e.g., arandomly generated number) that is associated with the invite. Thecomputing device sends the token with the invite to the computingsystem. The invite comprises the media content item, the event invitemedia overlay, and any additional metadata associated with the invite.The computing system receives the invite and token and stores the inviteand token in one or more datastores (e.g., databases 120). When usersjoin the event, the same token is used to send a request to thecomputing system to join the event and the token will allow them to jointhe group. In one example, the computing system generates a new groupfor the event, the new group comprising the user that set up the eventand any users that join the event (e.g., select to join the event viathe invite). The users that join the event are added to the group whenthey elect to join the event.

The custom event invite media overlay is displayed on the media contentitem on a user interface of a computing device associated with a userthat has been invited to the event (e.g., the second computing device ofthe second user). FIG. 10 illustrates an example GUI 1000 displaying thecustom event invite media overly 802 that is displayed on (e.g.,overlaid on) a media content item 804. In this example, the custom eventinvite media overlay 802 shows an event title 806, an event location808, an event date and time 810, an option 812 to view details of theevent, and an option 814 to join the event.

A user can select to view the details of the event (e.g., via option812) and the computing device associated with the user can display thedetails of the event or join the event (e.g., via option 814). FIG. 11illustrates an example GUI 1100 displaying the details of the event1102, information 1104 on how many other users have joined, a map 1106showing the location of the event, and an option 1108 to join the event.The map 1106 further shows locations of the users who have joined theevent (e.g., showing an avatar representing each user).

Once the user selects to join the event, the computing device sends arequest to the computing system (e.g., server system 108) along with thetoken corresponding to the event. The computing system receives therequest and token, determines the corresponding event to the token, andadds the user to the event (e.g., as a member of the group for theevent). The computing system logs information related to the user, suchas the date and time the user joined the event. In one example, thecomputing system logs various events related to the event. For example,the computing system logs each time a new user is added (joins) an eventand corresponding information, each time a user that has joined theevent invites another user to the event and corresponding information,any time an event changes and what changes were made, communicationsbetween users via the event group, and so forth.

In one example, the computing system generates notifications associatedwith the event. For example, the computing system generates anotification that the new user joined the event and sends thenotification to the computing device corresponding to the user thatcreated the event, to other users who have joined the event, and/or toother users that are invited to the event. The corresponding computingdevice receives the notification that the new user joined the event andcauses display of the notification on a display of the computing device.FIG. 12 illustrates an example display 1200 of a computing deviceshowing three example notifications that have been received by acomputing device. The first notification 1202 has information indicatingthat something in the event has changed (e.g., the location haschanged). The second notification 1204 has information indicating that anew user (Alex F.) has joined the event. The third notification 1206 hasinformation indicating that the user has received a new invite.

Once the computing system adds the user to the event, the computingsystem sends a response message to the computing device indicating thatthe user has successfully joined the event. The computing device candisplay an indication to the user that they have successfully joined theevent. In one example, the computing device displays a messageindicating that the user has joined in a chat interface to allow theuser to chat with other users that have joined the event. FIG. 13 is anexample GUI 1300 that includes a message 1302 indicating that the userhas successfully joined the event 1310 and allows the user to send amessage to the other users that have joined the event, such as by typingin a message in a dialog box 1304 via the keyboard 1306 or other means.The message the user and other users send will appear in the displaysection 1308, as shown in the example GUI 1400 of FIG. 14.

In one example embodiment, the computing device causes display of thechat session between users that have joined the event, wherein a userjoining an event can only view messages in the chat session thatoccurred after the user joined the event. Any messages in the chatsession before the user joined are visible to other users who havealready joined, but not to the new user that has just joined. Anymessages in the chat session that occur after the new user has joined,will be visible by the new user. In another example embodiment, when theuser joins the event, the user can view all messages that that occurredbefore joining.

In one example embodiment, the computing device causes display of a GUIshowing a list of users that have joined the event, a list of users thatwere invited but have not joined the event, and/or a list of usersinvited by a user other than the user that created the event that joinedthe event. FIG. 15 illustrates an example GUI 1500 that includes a list1502 of users that have joined the event, a list 1504 of users that wereinvited by a first user (Me), and a list 1506 of users that were invitedby a second user (Alexa). The GUI 1500 also include an option 1508 toinvite additional users to the event. For example, if a user chooses toinvite additional users, the invite comprising the media content itemand custom event invite media overlay will be sent to the additionalusers. In another example, the invite comprising the custom event invitemedia overlay can be sent directly to each of the additional users via achat session, as shown in the example GUI 1600 of FIG. 16. The userreceiving the invite can join directly via the chat session (e.g., viajoin option 1602).

In one example embodiment, any user can invite any other users to theevent. In another example embodiment, a user (e.g., a first user) canonly invite another user to the event if the first user is a “friend” ora “best friend” of the user who created the event (the creator user).For instance, the first user must be of a certain status in the socialnetwork of the creator user in order for the first user to be able tosend the invite to other users. The certain status can be set by thecreator user or as a default by the computing system.

In one example embodiment, a user can share an invite that someone elsecreated by adding the custom event invite media overlay to a mediacontent item created by the user. For example, a user can take a photoor video and then add the custom invite media overlay and send theinvite comprising the media content item and custom event invite mediaoverlay to one or more other users. In another example, a user can sharean invite by creating a new custom event invite media overlay thatallows users to join the same event group as the original invite (e.g.,the new custom event invite media overlay is linked to the originalinvite/event group).

In one example embodiment, users can optionally RSVP when joining theevent, or after joining the event. For example, the computing device cancause display of options for indicating whether the user will attend theevent. FIG. 17 illustrates an example GUI 1700 including options to RSVPfor the event. For example, the options include an option 1702indicating that the user has joined the event, an option 1704 that canbe selected to indicate that the user will attend the event, and anoption 1706 indicating that the user will not attend the event. The GUI1700 also includes messages indicating users that will be attending theevent (1708) and users that will not be attending the event (1710). Inone example, a user can still be part of the event group as long as theuser has joined the event, regardless whether the user has indicatedwhether he can or cannot attend the event.

In one example embodiment, the computing device causes an indication ofthe event to display on a map in a GUI on the computing device. Theindication of the event appears on the map at a location correspondingto the event and within a time period corresponding to the time of dayof the event. FIG. 18 illustrates an example GUI 1800 displaying a map1802 with an indication of the event in the form of a flag 1804. Theflag 1804 is at a location in the map corresponding to the location ofthe event. In one example, the indication of the event appears on themap within a specified time window. For example, the flag 1804 mayappear on the map a certain number of hours before a start time of theevent (e.g., 12 hours before the event starts) and can continue toappear for a certain number of hours after an end time of the event(e.g., 6 hours after the event ends).

In one example embodiment, the visual indication of the event canreflect a number of people that have arrived at the event. For example,the flag or a blimp or balloon representing the event can expand (e.g.,get bigger and bigger) the more people get to the event (and retract,e.g., get smaller and smaller as people leave the event).

In one example embodiment, the computing device causes display of anavatar (or other indicium) corresponding to each user that is currentlyattending the event (e.g., at the location of the event). In oneexample, the avatar is a visual representation of the user (e.g.,similar hair color or style, similar style, as the user). FIG. 19illustrates an example GUI 1900 displaying a map 1902 with an indicationof the event 1904 and an avatar 1906 for each user that is currentlylocated at the event. For example, the computing system (e.g., serversystem 108) detects that a user is in a location within a predefineddistance from the location of the event during a time period of theevent (e.g., after the event starts, between when the event starts andwhen the event ends) and sends the information to the computing deviceto cause the avatar (or other indicia) for the user to be displayed onthe map 1902 at the location of the event.

In one example embodiment, a user (e.g., the user that created theevent) can cancel the event, but the event group can stay active. Forexample, when the event is cancelled, the computing device sends arequest to cancel the event to a computing system. The computing systemreceives the request, stores an indication that the event is canceled,sends a notification to each user that joined the event that the eventhas been canceled, and changes the status and tile of the event toindicate that the event is canceled. The event group, however, canremain active so that the users that joined the event can continue tochat in a chat session.

In one example embodiment, users who are attending the event can capturemedia content items (e.g., images or video) and post them to the eventgroup. For example, the computing device or computing system candetermine that a user who has joined the event is capturing an image orvideo in a location of the event during the time of the event andautomatically post the image or video to the event group in the form ofa group story. The group story can be populated by media content itemscaptured by the users that have joined the event when they are attendingthe event. In one example, the media content items posted to the eventgroup are only viewable by those users that are part of the group.

For instance, a media content item can be captured on a computing devicevia a camera of the computing device. The computing device (or computingsystem) determines that the media content item is captured at a location(e.g., via GPS or similar technology of the computing device) and timeof day corresponding to the event. The computing device (or computingsystem) can automatically post the media content item to a group storyfor the event group, based on determining that the media content item iscaptured at a location and time of day corresponding to the event.

In one example embodiment, instead of automatically posting mediacontent items captured by users that have joined the event when they areattending the event, the computing device can include the group story ina destination list for sending the media content item. For example,after capturing the media content item, a user can select an option tosend the media content item to a destination (e.g., one or more usersand/or groups of users). The computing device can cause the event groupto appear in the destination list.

In one example embodiment, the destinations in the destination list areranked in an order of relevance. In this case, the event group can beranked higher in the list based on detecting that the user capturing themedia content item has captured the media content item while attendingthe event (e.g., has captured the media content item while in thelocation of the event during the time of the event). FIG. 20 illustratesan example GUI 2000 displaying a destination list 2002 with the eventgroup 2004 ranked first in the list. The user can select the event group2004 to post the media content item to the group story for the event.The group story or media content item may be ephemeral (e.g., availablefor viewing for only a predetermined amount of time) or could beavailable indefinitely.

For instance, a media content item can be captured on a computing devicevia a camera of the computing device. The computing device (or computingsystem) determines that the media content item is captured at a locationand time of day corresponding to the event. The computing device (orcomputing system) can rank options to which to send the media contentitem in a destination list wherein a media collection (group story)corresponding to the event is ranked higher in the destination listbased on determining that the media content item is captured at alocation and time of day corresponding to the event. The computingdevice (or computing system) causes display of the destination list withthe ranked options on a display of the computing device.

In one example, a graphic can be automatically generated and added tothe group story when certain events occur corresponding to the event.For example, a graphic can be generated and added to the group story forthe event group to indicate that a new user has joined the event. FIG.21 illustrates an example graphic 2102 generated to reflect an eventoccurring for the event. In this example, avatars 2104, 2106, 2108, and2110 representing some users that have joined are included in thegraphic 2102, and a message 2112 that a new user has joined is includedin the graphic 2102. The graphic 2102 is added to the media collection(group story for the event group).

In one example, the details of the event are integrated into a calendaron the computing device. The event details can be synced with the eventintegrated into the calendar to reflect any changes to the event (e.g.,location change, date or time change, cancellation).

FIG. 22 is a block diagram 2200 illustrating a software architecture2202, which can be installed on any one or more of the devices describedabove. For example, in various embodiments, client devices 110 andservers and systems 102, 112, 116, 118, 122, and 124 may be implementedusing some or all of the elements of the software architecture 2202.FIG. 22 is merely a non-limiting example of a software architecture, andit will be appreciated that many other architectures can be implementedto facilitate the functionality described herein. In variousembodiments, the software architecture 2202 is implemented by hardwaresuch as a machine 2300 of FIG. 23 that includes processors 2310, memory2330, and input/output I/O components 2350. In this example, thesoftware architecture 2202 can be conceptualized as a stack of layerswhere each layer may provide a particular functionality. For example,the software architecture 2202 includes layers such as an operatingsystem 2204, libraries 2206, frameworks 2208, and applications 2210.Operationally, the applications 2210 invoke API calls 2212 through thesoftware stack and receive messages 2214 in response to the API calls2212, consistent with some embodiments.

In various implementations, the operating system 2204 manages hardwareresources and provides common services. The operating system 2204includes, for example, a kernel 2220, services 2222, and drivers 2224.The kernel 2220 acts as an abstraction layer between the hardware andthe other software layers, consistent with some embodiments. Forexample, the kernel 2220 provides memory management, processormanagement (e.g., scheduling), component management, networking, andsecurity settings, among other functionality. The services 2222 canprovide other common services for the other software layers. The drivers2224 are responsible for controlling or interfacing with the underlyinghardware, according to some embodiments. For instance, the drivers 2224can include display drivers, camera drivers, BLUETOOTH® or BLUETOOTH®Low Energy drivers, flash memory drivers, serial communication drivers(e.g., Universal Serial Bus (USB) drivers), WI-FI® drivers, audiodrivers, power management drivers, and so forth.

In some embodiments, the libraries 2206 provide a low-level commoninfrastructure utilized by the applications 2210. The libraries 2206 caninclude system libraries 2230 (e.g., C standard library) that canprovide functions such as memory allocation functions, stringmanipulation functions, mathematic functions, and the like. In addition,the libraries 2206 can include API libraries 2232 such as medialibraries (e.g., libraries to support presentation and manipulation ofvarious media formats such as Moving Picture Experts Group-4 (MPEG4),Advanced Video Coding (H.264 or AVC), Moving Picture Experts GroupLayer-3 (MP3), Advanced Audio Coding (AAC), Adaptive Multi-Rate (AMR)audio codec, Joint Photographic Experts Group (JPEG or JPG), or PortableNetwork Graphics (PNG)), graphics libraries (e.g., an OpenGL frameworkused to render two-dimensional (2D) and three-dimensional (3D) graphiccontent on a display), database libraries (e.g., SQLite to providevarious relational database functions), web libraries (e.g., WebKit toprovide web browsing functionality), and the like. The libraries 2206can also include a wide variety of other libraries 2234 to provide manyother APIs to the applications 2210.

The frameworks 2208 provide a high-level common infrastructure that canbe utilized by the applications 2210, according to some embodiments. Forexample, the frameworks 2208 provide various graphic user interface(GUI) functions, high-level resource management, high-level locationservices, and so forth. The frameworks 2208 can provide a broad spectrumof other APIs that can be utilized by the applications 2210, some ofwhich may be specific to a particular operating system 2204 or platform.

In an example embodiment, the applications 2210 include a homeapplication 2250, a contacts application 2252, a browser application2254, a book reader application 2256, a location application 2258, amedia application 2260, a messaging application 2262, a game application2264, and a broad assortment of other applications such as a third-partyapplication 2266. According to some embodiments, the applications 2210are programs that execute functions defined in the programs. Variousprogramming languages can be employed to create one or more of theapplications 2210, structured in a variety of manners, such asobject-oriented programming languages (e.g., Objective-C, Java, or C++)or procedural programming languages (e.g., C or assembly language). In aspecific example, the third-party application 2266 (e.g., an applicationdeveloped using the ANDROID™ or IOS™ software development kit (SDK) byan entity other than the vendor of the particular platform) may bemobile software running on a mobile operating system such as IOS™,ANDROID™, WINDOWS® Phone, or another mobile operating system. In thisexample, the third-party application 2266 can invoke the API calls 2212provided by the operating system 2204 to facilitate functionalitydescribed herein.

Some embodiments may particularly include an event planning application2267. In certain embodiments, this may be a standalone application thatoperates to manage communications with a server system, such asthird-party servers or the server system 108. In other embodiments, thisfunctionality may be integrated with another application (e.g., themessaging application 2262). The event planning application 2267 mayrequest and display various data related to messaging, media content,media collections, media overlays, interactive messages, chat messages,and so forth, and may provide the capability for a user to input datarelated to the system via a touch interface, via a keyboard, or using acamera device of the machine 2300, communication with a server systemvia the I/O components 2350, and receipt and storage of object data inthe memory 2330. Presentation of information and user inputs associatedwith the information may be managed by the event planning application2267 using different frameworks 2208, library 2206 elements, oroperating system 2204 elements operating on the machine 2300.

FIG. 23 is a block diagram illustrating components of a machine 2300,according to some embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 23 shows a diagrammatic representation of the machine2300 in the example form of a computer system, within which instructions2316 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 2300 to perform any oneor more of the methodologies discussed herein can be executed. Inalternative embodiments, the machine 2300 operates as a standalonedevice or can be coupled (e.g., networked) to other machines. In anetworked deployment, the machine 2300 may operate in the capacity of aserver system 102, 112, 116, 118, 122, 124, and the like, or a clientdevice 110 in a server-client network environment, or as a peer machinein a peer-to-peer (or distributed) network environment. The machine 2300can comprise, but not be limited to, a server computer, a clientcomputer, a personal computer (PC), a tablet computer, a laptopcomputer, a netbook, a personal digital assistant (PDA), anentertainment media system, a cellular telephone, a smart phone, amobile device, a wearable device (e.g., a smart watch), a smart homedevice (e.g., a smart appliance), other smart devices, a web appliance,a network router, a network switch, a network bridge, or any machinecapable of executing the instructions 2316, sequentially or otherwise,that specify actions to be taken by the machine 2300. Further, whileonly a single machine 2300 is illustrated, the term “machine” shall alsobe taken to include a collection of machines 2300 that individually orjointly execute the instructions 2316 to perform any one or more of themethodologies discussed herein.

In various embodiments, the machine 2300 comprises processors 2310,memory 2330, and I/O components 2350, which can be configured tocommunicate with each other via a bus 2302. In an example embodiment,the processors 2310 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a radio-frequency integrated circuit (RFIC), another processor,or any suitable combination thereof) include, for example, a processor2312 and a processor 2314 that may execute the instructions 2316. Theterm “processor” is intended to include multi-core processors 2310 thatmay comprise two or more independent processors 2312, 2314 (alsoreferred to as “cores”) that can execute instructions 2316contemporaneously. Although FIG. 23 shows multiple processors 2310, themachine 2300 may include a single processor 2310 with a single core, asingle processor 2310 with multiple cores (e.g., a multi-core processor2310), multiple processors 2312, 2314 with a single core, multipleprocessors 2312, 2314 with multiple cores, or any combination thereof.

The memory 2330 comprises a main memory 2332, a static memory 2334, anda storage unit 2336 accessible to the processors 2310 via the bus 2302,according to some embodiments. The storage unit 2336 can include amachine-readable medium 2318 on which are stored the instructions 2316embodying any one or more of the methodologies or functions describedherein. The instructions 2316 can also reside, completely or at leastpartially, within the main memory 2332, within the static memory 2334,within at least one of the processors 2310 (e.g., within the processor'scache memory), or any suitable combination thereof, during executionthereof by the machine 2300. Accordingly, in various embodiments, themain memory 2332, the static memory 2334, and the processors 2310 areconsidered machine-readable media 2318.

As used herein, the term “memory” refers to a machine-readable medium2318 able to store data temporarily or permanently and may be taken toinclude, but not be limited to, random-access memory (RAM), read-onlymemory (ROM), buffer memory, flash memory, and cache memory. While themachine-readable medium 2318 is shown, in an example embodiment, to be asingle medium, the term “machine-readable medium” should be taken toinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) able to storethe instructions 2316. The term “machine-readable medium” shall also betaken to include any medium, or combination of multiple media, that iscapable of storing instructions (e.g., instructions 2316) for executionby a machine (e.g., machine 2300), such that the instructions 2316, whenexecuted by one or more processors of the machine 2300 (e.g., processors2310), cause the machine 2300 to perform any one or more of themethodologies described herein. Accordingly, a “machine-readable medium”refers to a single storage apparatus or device, as well as “cloud-based”storage systems or storage networks that include multiple storageapparatus or devices. The term “machine-readable medium” shallaccordingly be taken to include, but not be limited to, one or more datarepositories in the form of a solid-state memory (e.g., flash memory),an optical medium, a magnetic medium, other non-volatile memory (e.g.,erasable programmable read-only memory (EPROM)), or any suitablecombination thereof. The term “machine-readable medium” specificallyexcludes non-statutory signals per se.

The I/O components 2350 include a wide variety of components to receiveinput, provide output, produce output, transmit information, exchangeinformation, capture measurements, and so on. In general, it will beappreciated that the I/O components 2350 can include many othercomponents that are not shown in FIG. 23. The I/O components 2350 aregrouped according to functionality merely for simplifying the followingdiscussion, and the grouping is in no way limiting. In various exampleembodiments, the I/O components 2350 include output components 2352 andinput components 2354. The output components 2352 include visualcomponents (e.g., a display such as a plasma display panel (PDP), alight emitting diode (LED) display, a liquid crystal display (LCD), aprojector, or a cathode ray tube (CRT)), acoustic components (e.g.,speakers), haptic components (e.g., a vibratory motor), other signalgenerators, and so forth. The input components 2354 include alphanumericinput components (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point-based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstruments), tactile input components (e.g., a physical button, a touchscreen that provides location and force of touches or touch gestures, orother tactile input components), audio input components (e.g., amicrophone), and the like.

In some further example embodiments, the I/O components 2350 includebiometric components 2356, motion components 2358, environmentalcomponents 2360, or position components 2362, among a wide array ofother components. For example, the biometric components 2356 includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 2358 includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 2360 include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometers that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components (e.g.,infrared sensors that detect nearby objects), gas sensor components(e.g., machine olfaction detection sensors, gas detection sensors todetect concentrations of hazardous gases for safety or to measurepollutants in the atmosphere), or other components that may provideindications, measurements, or signals corresponding to a surroundingphysical environment. The position components 2362 include locationsensor components (e.g., a Global Positioning System (GPS) receivercomponent), altitude sensor components (e.g., altimeters or barometersthat detect air pressure from which altitude may be derived),orientation sensor components (e.g., magnetometers), and the like.

Communication can be implemented using a wide variety of technologies.The I/O components 2350 may include communication components 2364operable to couple the machine 2300 to a network 2380 or devices 2370via a coupling 2382 and a coupling 2372, respectively. For example, thecommunication components 2364 include a network interface component oranother suitable device to interface with the network 2380. In furtherexamples, communication components 2364 include wired communicationcomponents, wireless communication components, cellular communicationcomponents, near field communication (NFC) components, BLUETOOTH®components (e.g., BLUETOOTH® Low Energy), WI-FI® components, and othercommunication components to provide communication via other modalities.The devices 2370 may be another machine 2300 or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a UniversalSerial Bus (USB)).

Moreover, in some embodiments, the communication components 2364 detectidentifiers or include components operable to detect identifiers. Forexample, the communication components 2364 include radio frequencyidentification (RFID) tag reader components, NFC smart tag detectioncomponents, optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as a Universal Product Code (UPC) barcode, multi-dimensional bar codes such as a Quick Response (QR) code,Aztec Code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code,Uniform Commercial Code Reduced Space Symbology (UCC RSS)-2D bar codes,and other optical codes), acoustic detection components (e.g.,microphones to identify tagged audio signals), or any suitablecombination thereof. In addition, a variety of information can bederived via the communication components 2364, such as location viaInternet Protocol (IP) geolocation, location via WI-FI® signaltriangulation, location via detecting a BLUETOOTH® or NFC beacon signalthat may indicate a particular location, and so forth.

In various example embodiments, one or more portions of the network 2380can be an ad hoc network, an intranet, an extranet, a virtual privatenetwork (VPN), a local area network (LAN), a wireless LAN (WLAN), a widearea network (WAN), a wireless WAN (WWAN), a metropolitan area network(MAN), the Internet, a portion of the Internet, a portion of the publicswitched telephone network (PSTN), a plain old telephone service (POTS)network, a cellular telephone network, a wireless network, a WI-FI®network, another type of network, or a combination of two or more suchnetworks. For example, the network 2380 or a portion of the network 2380may include a wireless or cellular network, and the coupling 2382 may bea Code Division Multiple Access (CDMA) connection, a Global System forMobile communications (GSM) connection, or another type of cellular orwireless coupling. In this example, the coupling 2382 can implement anyof a variety of types of data transfer technology, such as SingleCarrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized(EVDO) technology, General Packet Radio Service (GPRS) technology,Enhanced Data rates for GSM Evolution (EDGE) technology, thirdGeneration Partnership Project (3GPP) including 3G, fourth generationwireless (4G) networks, Universal Mobile Telecommunications System(UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability forMicrowave Access (WiMAX), Long Term Evolution (LTE) standard, othersdefined by various standard-setting organizations, other long rangeprotocols, or other data transfer technology.

In example embodiments, the instructions 2316 are transmitted orreceived over the network 2380 using a transmission medium via a networkinterface device (e.g., a network interface component included in thecommunication components 2364) and utilizing any one of a number ofwell-known transfer protocols (e.g., Hypertext Transfer Protocol(HTTP)). Similarly, in other example embodiments, the instructions 2316are transmitted or received using a transmission medium via the coupling2372 (e.g., a peer-to-peer coupling) to the devices 2370. The term“transmission medium” shall be taken to include any intangible mediumthat is capable of storing, encoding, or carrying the instructions 2316for execution by the machine 2300, and includes digital or analogcommunications signals or other intangible media to facilitatecommunication of such software.

Furthermore, the machine-readable medium 2318 is non-transitory (inother words, not having any transitory signals) in that it does notembody a propagating signal. However, labeling the machine-readablemedium 2318 “non-transitory” should not be construed to mean that themedium is incapable of movement; the machine-readable medium 2318 shouldbe considered as being transportable from one physical location toanother. Additionally, since the machine-readable medium 2318 istangible, the machine-readable medium 2318 may be considered to be amachine-readable device.

Throughout this specification, plural instances may implementcomponents, operations, or structures described as a single instance.Although individual operations of one or more methods are illustratedand described as separate operations, one or more of the individualoperations may be performed concurrently, and nothing requires that theoperations be performed in the order illustrated. Structures andfunctionality presented as separate components in example configurationsmay be implemented as a combined structure or component. Similarly,structures and functionality presented as a single component may beimplemented as separate components. These and other variations,modifications, additions, and improvements fall within the scope of thesubject matter herein.

Although an overview of the inventive subject matter has been describedwith reference to specific example embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader scope of embodiments of the present disclosure.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Moreover, plural instances may be provided forresources, operations, or structures described herein as a singleinstance. Additionally, boundaries between various resources,operations, modules, engines, and data stores are somewhat arbitrary,and particular operations are illustrated in a context of specificillustrative configurations. Other allocations of functionality areenvisioned and may fall within a scope of various embodiments of thepresent disclosure. In general, structures and functionality presentedas separate resources in the example configurations may be implementedas a combined structure or resource. Similarly, structures andfunctionality presented as a single resource may be implemented asseparate resources. These and other variations, modifications,additions, and improvements fall within a scope of embodiments of thepresent disclosure as represented by the appended claims. Thespecification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A method comprising: detecting, by a firstcomputing device, a selection of an interface element displayed on amedia content item to add an event invite media overlay to the mediacontent item; automatically resizing the custom invite media overlayfrom an original size to a resized custom event invite media overlaybased on content added to the event media overlay; sending, to a secondcomputing device, the invitation to attend the event comprising theresized custom event invite media overlay overlaid on the media contentitem; and receiving a notification indicating that a user associatedwith the second computing device joined the event.
 2. The method ofclaim 1, further comprising: displaying a message in a chat sessionbetween users that have joined the event, the message indicating that anew user has joined the event and adding the new user to the chatsession.
 3. The method of claim 1, wherein a media collection isassociated with the event and further comprising: in response todetermining that a new user has joined the event, automaticallygenerating a graphic comprising an avatar of the new user and a messageindicating that the new user has joined the event; and adding thegenerated graphic to the media collection.
 4. The method of claim 1,further comprising: displaying a chat session between users that havejoined the event, wherein a user joining an event can only view messagesin the chat session that occurred after the user joined the event. 5.The method of claim 1, wherein the media content item comprises an imageor video.
 6. The method of claim 1, wherein the event invite mediaoverlay is in the form of a sticker.
 7. The method of claim 1, whereinthe content added to the event comprises at least one of a title, alocation, a date, or a time of day.
 8. The method of claim 1, whereinthe first computing device is associated with a first user and themethod further comprises: displaying a list of users that have joinedthe event, a list of users that were invited but have not joined theevent, and a list of users invited by a second user that has joined theevent.
 9. The method of claim 1, further comprising: displaying anindication of the event on a map in the user interface on the firstcomputing device, the indication of the event appearing on the map at alocation corresponding to the event and within a specified time periodcorresponding to the time of day of the event.
 10. The method of claim9, further comprising: displaying an avatar corresponding to each userthat is currently attending the event, with the indication of the eventon the map.
 11. The method of claim 1, further comprising: capturing asecond media content item via a camera device of the computing device;determining that the second media content item is captured at a locationand time of day corresponding to the event; ranking options to which tosend the second media content item in a destination list wherein a mediacollection corresponding to the event is ranked higher in thedestination list based on determining that the second media content itemis captured at the location and time of day corresponding to the event;and displaying the destination list with the ranked options.
 12. Themethod of claim 1, further comprising: receiving notification that theuser associated with the second computing device sent the invite to theevent comprising the custom event invite media overlay to a thirdcomputing device associated with a third user; and displaying thenotification on a display of the first computing device.
 13. The methodof claim 1, further comprising: generating a token comprising a uniqueidentifier for the invite; and sending the token to a server systemwherein the token is correlated with the content corresponding to theevent.
 14. A computing device comprising: a memory that storesinstructions; and one or more processors configured by the instructionsto perform operations comprising: detecting a selection of an interfaceelement displayed on a media content item to add an event invite mediaoverlay to the media content item; automatically resizing the custominvite media overlay from an original size to a resized custom eventinvite media overlay based on content added to the event media overlay;sending, to a second computing device, the invitation to attend theevent comprising the resized custom event invite media overlay overlaidon the media content item; and receiving a notification indicating thata user associated with the second computing device joined the event. 15.The computing device of claim 14, the operations further comprising:displaying a message in a chat session between users that have joinedthe event, the message indicating that a new user has joined the eventand adding the new user to the chat session.
 16. The computing device ofclaim 14, wherein a media collection is associated with the event andthe operations further comprise: in response to determining that a newuser has joined the event, automatically generating a graphic comprisingan avatar of the new user and a message indicating that the new user hasjoined the event; and adding the generated graphic to the mediacollection.
 17. The computing device of claim 14, the operations furthercomprising: displaying a chat session between users that have joined theevent, wherein a user joining an event can only view messages in thechat session that occurred after the user joined the event.
 18. Thecomputing device of claim 14, the operations further comprising:displaying an indication of the event on a map in a user interface onthe computing device, the indication of the event appearing on the mapat a location corresponding to the event and within a specified timeperiod corresponding to the time of day of the event.
 19. The computingdevice of claim 14, the operations further comprising: capturing asecond media content item via a camera device of the computing device;determining that the second media content item is captured at a locationand time of day corresponding to the event; ranking options to which tosend the second media content item in a destination list wherein a mediacollection corresponding to the event is ranked higher in thedestination list based on determining that the second media content itemis captured at the location and time of day corresponding to the event;and displaying the destination list with the ranked options.
 20. Anon-transitory computer-readable medium comprising instructions storedthereon that are executable by at least one processor to cause acomputing device to perform operations comprising: detecting a selectionof an interface element displayed on a media content item to add anevent invite media overlay to the media content item; automaticallyresizing the custom invite media overlay from an original size to aresized custom event invite media overlay based on content added to theevent media overlay; sending, to a second computing device, theinvitation to attend the event comprising the resized custom eventinvite media overlay overlaid on the media content item; and receiving anotification indicating that a user associated with the second computingdevice joined the event.